home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
ndscn110.arc
/
NODESCAN.DOC
< prev
next >
Wrap
Text File
|
1991-02-04
|
9KB
|
245 lines
*** ** **
**** ** **
** ** ** **** ***** **** **** ***** *** **
** ** ** ** ** ** ** ** ** ** ** ** *****
** **** ** ** ** ** ****** **** ** **** ** **
** *** ** ** ** ** ** ** ** ** ** ** **
** ** **** ****** **** **** ***** ***** ** **
Version 1.1
Copyright (C) 1990
by Michel Renaud
Hull, Québec, Canada
FidoNet 1:163/211.6
DISCLAIMER OF WARRANTY
======================
There is only one guarantee: Nodescan works fine on MY computer. I
will not be held responsible for any problems/damages Nodescan may
cause on your system. USE AT YOUR OWN RISK.
FREEWARE
========
This program is FREEWARE. First, that means it is FREE. You should
not charge for the distribution or use of Nodescan. Second, it should
be distributed in its original form, that is, the executable file
NODESCAN.EXE and the documentation (NODESCAN.DOC). Third, the program
should not be modified in any way.
INTRODUCTION
============
Nodescan reads an AREAS.BBS-type file and output the total number of
addresses and echos listed into it. It will also output the number of
echos for each address and the total number of single feeds (echos with
only one node listed).
The idea comes from Ken Wilson, the Region 12 EchoMail Co-ordinator and
SysOp of the Ned's Opus Bulletin Board in Ottawa, Ontario, Canada. I
originally wrote the utility with only Ken's REC system in mind, but a
few days after its release on SDS, bug reports and suggestions came
from a couple of sysop in North America and Europe. I then decided to
go on and write some documentation, and add a few options to support
other zones and short forms of areas file.
This program is FREEWARE. You may not charge for its distribution or
use. I do not expect any money from you. Either you like it or you
hate it. In either case, I would like to hear from you, just for my
own satisfaction :-)
Nodescan was written using Turbo C++ 1.0 (in ANSI C mode) from Borland
International. The CXL v5.2 library by Mike Smedley was used for
string handling.
BUG REPORTS/SUGGESTIONS
=======================
If you experience any problem with Nodescan, you can always write to me
via FidoNet netmail at 1:163/211.6. I will do my best to find a
solution to your problem. Please include any system-specific
information you may find useful. A copy of your AREAS.BBS file would
help me too.
Any suggestions may also be sent to 1:163/211.6.
Keep in mind that I work on Nodescan on my spare time only. I will do
my best to enhance or fix Nodescan, but do not expect
commercial-quality service from me.
USING NODESCAN
==============
Nodescan is very simple to use. The only required parameter is the
filename of an AREAS.BBS-type file. You may add other parameters to
specify the sort method to be used and the default zone number.
Syntax:
=======
NODESCAN <filename> [/a /e /n] [/z:<zone>] [/q] [/? /H]
where:
<filename> is the filename of the areas file to be scanned. You
may enter only the filename if the file is in the current
directory, or a full pathname. This parameter is required.
/a to sort the output list by address.
/e to sort the output list by number of echos.
/n no sort.
/z:<zone> specify the zone number. The default zone number is 1.
If you were in zone 2 you would enter /Z:2
/q quiet mode. Suppresses the display of "Reading..." and
"Sorting..." messages.
/? and /H display the help screen.
Nodescan will only accept one parameter of each type. That is, if you
enter:
NODESCAN areas.bbs /a /e /z:2 /z:1
Nodescan will ignore the /e and /z:1.
Nodescan will also ignore incorrect parameters, as long as the required
parameter (the filename) is specified.
PRINTING THE OUTPUT
===================
You can use the MS-DOS output redirection operator (>) to send
Nodescan's output to a disk file or to the printer.
eg.
NODESCAN areas.bbs>prn
NODESCAN areas.bbs>nodescan.out
While processing a file, Nodescan displays the messages "Reading
<filename>" and "Sorting". They are being sent to stderr, that is, the
screen. Redirected output will not contain these messages.
LIMITATIONS
===========
Nodescan currently have the following limitations:
- The maximum number of different addresses that can be handled is
256.
- The maximum line length in AREAS.BBS is 512 characters.
A future release of Nodescan will allocate memory dynamically, making
the maximum number of addresses limited only by available memory (and
reducing the memory requirements if you have less than 256 nodes in
your AREAS.BBS).
NOTES ABOUT YOUR AREAS.BBS
==========================
Nodescan will handle the long and short forms of AREAS.BBS files.
Nodescan assumes the following about your file:
- the system and sysop name are on the first line of the file and
are separated by an exclamation mark (!).
- the system name is no longer than 128 characters.
- the sysop name is no longer than 128 characters.
- ignores lines starting with a '-' or ';'
- assumes that a line containing a '/' contains at least one valid
address and will process this line (except if the line starts with
'-' or ';').
- assumes that you don't have any address longer than something
like "1:50000/50000".
HISTORY
=======
10/05/90 version 1.1
- Added documentation.
- Corrected two bugs in the sort routines:
- it would hang the machine if the areas file contained
addresees with more than 10 characters (eg. 1:1111/1111).
This has been fixed and Nodescan can now handle addresses
containing up to 13 characters (see LIMITATIONS).
- the address sort wasn't sorting properly.
- Added support for short form files.
- Added support for zones.
- Maximum number of addresses increased from 128 to 256.
- Added output of total single feeds in the file.
09/10/90 Version 1.00
Initial release.
CREDITS
=======
I would like to thank the following people who helped in the
development of Nodescan:
- Ken Wilson (1:163/211) who came up with the original idea and
then suggested a few additions to the initial release. Nodescan
would not exist without him.
- George Peace (1:13/13) was the first person to bring the sort
problem to my attention.
- John Burden (2:255/1) who confirmed that the sort routine had a
real problem <grin>. Without this guy Nodescan would probably not
support short form areas file and zone numbers.
- Did I forget someone? :-)
FUTURE RELEASES
===============
I plan to modify the program to allocate memory dynamically using a
linked list instead of a static array. This will make the maximum
number of addresses limited only by available memory, and reduce the
memory requirements for those of you who have small areas file.
Better handling of printer output. Page headers and page numbers, that
kind of stuff.
Any suggestions are welcome... netmail to 1:163/211.6